home *** CD-ROM | disk | FTP | other *** search
- Path: news.wwa.com!news
- From: pdubois@wwa.com (PDuBois)
- Newsgroups: comp.lang.c++
- Subject: Re: Borland 4.5 application won't work on its own
- Date: Wed, 13 Mar 1996 03:12:49 GMT
- Organization: SaturnSoft
- Message-ID: <4i5eb7$oe0@kirin.wwa.com>
- References: <4i3fhh$bor@dole.uninett.no>
- NNTP-Posting-Host: pool2-027.wwa.com
- X-Newsreader: Forte Free Agent 1.0.82
-
- Kristoffer.Moe@nifu.no (Kristoffer Moe) wrote:
-
- >I have recently developed an application with Borland C++
- >4.5 and OWL. It is based on a TDecoratedFrame parent with a TDialog as a
- >child. The program works nicely (acceptably that is) when compiled and run
- >'within' Borland IDE. However, when it is started on its own, whithout the
- >Borland IDE loaded in the machine at all, it displays the TDecoratedFrame,
- >and generates a General Protecton Fault. With Winspector running in the
- >background it works again. The application is based on AppExpert.
-
- >Ideas, anyone?
-
-
- >Yours,
-
-
-
- >Kristoffer Moe
-
- >Kristoffer.Moe@nifu.no
-
- Kristoffer,
-
- This is a common problem. You are using Borloand custom controls in
- your window or on one of your dialogs. When you do, you need to call
- EnableBWCCC() function in your TApplication's InitMainWindow function.
- This loads the Borland DLL that is needed to use their custome
- controls. The reason it throws a lot of people is because the Borland
- IDE and Borland Code Gaurd both load the DLL themselves, so you dont
- get an error when THEY are running. You only get the error when you
- run ther program by itself.
-
- Paul
-
-